Phone Applications Update

Purpose:

Use this form to upload screen saver, branding, and applications for distribution to supported 53xx and 69xx IP phones.

The distribution of apps is automatic for 69xx phones. For 53xx phones, the distribution happens when apps (HTML) are assigned to phones in the User and Services Configuration form.

The applications that are supported include:

• GUI Replacement and Notification apps (HTML), supported only on the 53xx phones. For a complete list of apps, see the HTML Toolkit Developer's Guide on the Mitel Document Center website.

• XML applications, supported only on the 69xx phones. The XML applications allow the 69xx phones to integrate with Mitel applications, such as:

• MiCollab Meeting Center. For configuration information, refer to Appendix A MiCollab Meeting Center Configuration in the MiCollab Client Administrator Guide, Release 8.0 on Mitel Document Center.

• Mitel Mass Notification. For configuration information, refer to the Mitel Mass Notification Installation, Administration, and Maintenance Guide, on Mitel InfoChannel.

Supported file types are:

• .png for branding images for 69xx phones

• .zip file for screen saver for 69xx phones

• .cfg for configuring XML applications for 69xx phones

• .spx The file extension for files created by the Mitel HTML Toolkit Packager. An SPX file consists of individual files bundled together. HTML capable phones extract the individual files which are used for branding, screen savers, and other applications. See the HTML Toolkit Developer's Guide on the Mitel eDocs website for more information. for 53xx phones

NOTE: XML/HTML applications, branding and screen-savers are not supported for the 6905 and 6910 IP Phones.

NOTE: Branding images for 69xx phones must be in PNG format. Otherwise, JPG is the recommended format due to smaller file size and faster loading time.

A screen saver is a collection of two or three images packaged in a .zip file that the phones cycle through when idle. File extraction (unzipping) and validation occurs on the phone after the file is downloaded to it. No validation is done by the form.

Branding refers to the background image (typically a corporate logo) displayed on an idle phone. The image replaces the screen saver.

69xx apps use fixed file names that begin with the app type (Branding, screen saver, or XML applications) followed by a dash (-), the phone model, and the file extension in lowercase. Examples:

• Branding-6920.png

• ScreenSaver-6940.zip

• AppInfo-6940.cfg

The screen saver .zip file must be 3 MB or smaller and contain no more than three images.

The size limit for the branding PNG file is 1 MB.

You can only upload files one at a time. If the system is part of an Administration Group, the file also can be uploaded to them at the same time. However, you can only delete files from one system at a time.

IMPORTANT: To upload, each Admin Group member element must have its security certificate trusted by the browser. FireFox users may need to trust each element twice depending on whether its host name or IP address was entered in the local Network Elements form. If the host name (i.e., FQDN) was entered, you will need to trust that plus the IP address. Internet Explorer users only need to trust one or the other.

NOTE: This form is an alternative to using the HTMLAppUpgrade maintenance command to update apps on 53xx IP phones.

Conditions

• Gray scale images can cause screen 'burn in' on 53xx phones. Use only black and white images for branding applications on these devices.

• Select a branding image that does not overlap areas of the 69xx phones display reserved for calling party information, advisory messages, and other or other. In general, the image should be sized and positioned to fit within the region of the display marked "Safe Area" as shown below:

Click image to enlarge

To approximate size and placement, open the image in a bitmap editor and set up a page with the same dimensions as the phone's display (see table below). Make the page background transparent. Then, add the image and position it in the area indicated above. Save the image and upload to a phone to confirm that the image is displaying correctly. You may need to experiment with different images and placements to achieve the desired result.

• 69xx IP phones can also retrieve screen saver and branding files from an external server by entering the URL of server in the Online Service URL form. If an URL is not specified, then the phones retrieve the files from the TFTP server using the IP address specified in the phones. If the TFTP server IP address is different from the MiVoice Business system IP address, then the screen saver and branding files must be uploaded to the TFTP server in the MiVoice Business system. If an external TFTP server is used, then screen saver and branding files must be manually uploaded to the external TFTP server.

• The 5360 and all 69xx phones have a factory default screen saver. If there is no screen saver to download, the default is used. To revert the 69xx to its default factory screen saver, delete the appropriate screen saver files from this form. For the 53xx, you can delete the current entry from this form or use the Phone Application tab in the User and Service Configuration form.

• There is no factory default branding application for any phones.

• The number and size of files that can be uploaded is limited only by the amount of available disk space on system. There is, however, a limit to the size of files that the phones can store. There are also limits on image dimensions (width/height) and color depth. These limits for 53xx phones are discussed in the HTML Toolkit Developer's Guide on the Mitel Document Center website. Limits for 69xx phones are as follows:

• On the EX, MXe III, CX II, CXi II, and AX platforms, you can have files in the same directory with names that differ only in case. For example, the following filenames can coexist in one directory:

image.png
Image.png
IMAGE.png

On server-basedMiVoice Business for Industry Standard Server, MiVoice Business Virtual MiVoice Business platforms, which have a case-insensitive file system, only one variant of the file is allowed. This means a file downloaded to a phone will replace one already there if the names match and the case does or does not.

• The Phone Application Update form cannot be used to upload apps to phones (for example, teleworker devices) connected to the system through MiVoice Border Gateway.

Field Descriptions